Method and system for providing offers for automated retail machines via mobile devices

ABSTRACT

A mobile device with a display, processor(s), and memory: identifies a retail machine configured for wireless communications based on broadcasted information transmitted by the retail machine and including an identifier corresponding to the retail machine; transmits the identifier to a server and receives from the server an electronic communication including a promotional offer for products or services offered by the retail machine; displays the promotional offer; detects selection of a promotional offer; receives a notification from the retail machine that a product or service was provided by the retail machine for a user of the mobile device; transmits confirmation information associated with the notification to the server, receives promotion validation information from the server indicating validation of the promotional offer; and based on the promotion validation information, displays information confirming application of the promotional offer.

PRIORITY CLAIM AND RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/029,483, filed Jul. 6, 2018, entitled “Method and System forProviding Offers for Automated Retail Machines Via Mobile Devices,”which is a continuation of Ser. No. 14/611,065, filed Jan. 30, 2015,entitled “Method and System for Providing Offers for Automated RetailMachines Via Mobile Devices,” now U.S. Pat. No. 10,019,724, issued onJul. 10, 2018, both of which are hereby expressly incorporated byreference in their entirety.

This application is related to the following: U.S. Pat. No. 8,856,045,filed Mar. 14, 2014, entitled “Mobile-Device-to-Machine PaymentSystems”; U.S. patent application Ser. No. 14/320,534, filed Jun. 30,2014, entitled “Method and System for Authenticating MobileDevice-to-Machine Payments”; U.S. patent application Ser. No.14/335,762, filed Jul. 18, 2014, entitled “Method and System forPerforming Mobile Device-To-Machine Payments”; U.S. patent applicationSer. No. 14/456,683, filed Aug. 11, 2014, entitled “Method and Devicefor Retrofitting an Offline-Payment Operated Machine to AcceptElectronic Payments”; U.S. patent application Ser. No. 14/458,192, filedAug. 12, 2014, entitled “Method and System for Retrofitting anOffline-Payment Operated Machine to Accept Electronic Payments”; andU.S. Provisional Patent Application No. 62/081,492, filed Nov. 11, 2014,entitled “Method and Device for Multi-Drop Bus Payment PeripheralExpansion,” all of which are hereby incorporated by reference in theirentireties.

TECHNICAL FIELD

The present application relates to the field of payment processingsystems, and in particular, to a mobile-device-to-machine paymentprocessing system over a non-persistent network connection.

BACKGROUND

Vending machines (or more broadly “automatic retail machines”), in thebroadest sense, have been around for thousands of years. The firstsimple mechanical coin operated vending machines were introduced in the1880s. Modern vending machines stock many different types of productsincluding, but not limited to drinks (e.g., water, juice, coffee, andsoda) and edible food products/items (e.g., snacks, candy, fruit, andfrozen meals), as well as a wide variety of non-food items. In this fastpaced world, vending machines are ubiquitous.

Vending machines are one type of “payment accepting unit” (paymentaccepting units are also referred to herein generically as “machines”).A payment accepting unit (or machine) is equipment that requires paymentfor the dispensing of products and/or services. In addition to vendingmachines, payment accepting units can also be other machines thatrequire payment for the dispensing of a product and/or servicesincluding, but not limited to parking meters, toll booths, laundromatwashers and dryers, arcade games, kiosks, photo booths, toll booths,transit ticket dispensing machines, and other known or yet to bediscovered payment accepting units.

In using a payment accepting unit, a user will (1) approach the paymentaccepting unit, (2) determine from the face of the payment acceptingunit the product (or service) he/she desires, (3) insert payment (e.g.,coins, bills, or payment cards), and (4) input his/her selection intothe payment accepting unit using a user interface (e.g., a series ofbuttons, a key pad, touch screen, or other input mechanism using, forexample, the column and row at which a product is located). Based on theuser's inputted selection, technology within the payment accepting unitprovides the desired product (or service) to the user.

As the number of people with Internet-connected mobile devicesproliferates, so does the variety of uses for such devices. Mobilepayment is a logical extension. There is a large development effortaround bringing mobile payment to the retail sector in an effort to notonly provide options to the user, but also increased convenience.

SUMMARY

In some implementations, a method of providing and handling promotionaloffers for an automatic retail machine is performed at a mobile device(e.g., the mobile device 104, FIGS. 1-2) with a display, one or moreprocessors, and memory. The method includes: displaying one or morepromotional offers on the display; detecting a user input selecting arespective promotional offer of the one or more promotional offers; andinitiating performance of a transaction with an automatic retail machinecoupled with a payment module, where the transaction corresponds topurchase of a product stocked by the automatic retail machine. Themethod also includes: receiving a transaction completion notificationfrom the payment module, where the transaction completion notificationindicates that the product corresponding to the selected respectivepromotional offer was vended by the automatic retail machine; and, inresponse to receiving the transaction completion notification, providinga prompt to the user of the mobile device to obtain a product code forthe vended product to validate the respective promotional offer. Themethod further includes: obtaining the product code for the vendedproduct; after obtaining the product code, transmitting the product codeto the server; and, in response to transmitting the product code:receiving promotion validation information from the server; anddisplaying the promotion validation information on the display, wherethe promotion validation information indicates whether the respectivepromotion offer was validated.

In some implementations, a mobile device (e.g., the mobile device 104,FIGS. 1-2) includes a display, one or more processors, and memorystoring one or more programs for execution by the one or moreprocessors, the one or more programs include instructions forperforming, or controlling performance of, the operations of any of themethods described herein. In some implementations, a non-transitorycomputer readable storage medium storing one or more programs, the oneor more programs comprising instructions, which, when executed by amobile device (e.g., the mobile device 104, FIGS. 1-2) with one or moreprocessors and a display, cause the computing device to perform, orcontrol performance of, the operations of any of the methods describedherein. In some implementations, a mobile device (e.g., the mobiledevice 104, FIGS. 1-2) includes means for performing, or controllingperformance of, the operations of any of the methods described herein.

Various advantages of the present application are apparent in light ofthe descriptions below.

BRIEF DESCRIPTION OF THE DRAWINGS

The aforementioned features and advantages of the disclosed technologyas well as additional features and advantages thereof will be moreclearly understood hereinafter as a result of a detailed description ofpreferred implementations when taken in conjunction with the drawings.

To describe the technical solutions in the implementations of thepresent disclosed technology or in the prior art more clearly, thefollowing briefly introduces the accompanying drawings required fordescribing the implementations or the prior art. Apparently, theaccompanying drawings in the following description show merely someimplementations of the present disclosed technology, and persons ofordinary skill in the art may still derive other drawings from theseaccompanying drawings without creative efforts.

FIG. 1 is a block diagram of a payment processing system in accordancewith some implementations.

FIG. 2 is a block diagram of a mobile device in accordance with someimplementations.

FIG. 3 is a block diagram of a server system in accordance with someimplementations.

FIG. 4 is a schematic block diagram of an automatic retail machine inaccordance with some implementations.

FIG. 5 is a block diagram of a payment module in accordance with someimplementations.

FIG. 6A is a perspective view of the payment module of FIG. 5 (e.g., anin-line dongle adapter) in accordance with some implementations.

FIG. 6B is a perspective view taken from the first end of the paymentmodule of FIG. 6A in accordance with some implementations.

FIG. 6C is a perspective view taken from the second end of the paymentmodule of FIG. 6A in accordance with some implementations.

FIG. 7 is a perspective view of the payment module of FIG. 6A within theautomatic retail machine of FIG. 4 in accordance with someimplementations.

FIG. 8 is a schematic flow diagram of a process for initiating atransaction in accordance with some implementations.

FIG. 9 is a schematic flow diagram of a process for acknowledging atransaction in accordance with some implementations.

FIG. 10A is a block diagram of an information packet broadcast by thepayment module in accordance with some implementations.

FIG. 10B is a block diagram of an authorization request in accordancewith some implementations.

FIG. 10C is a block diagram of an authorization grant token inaccordance with some implementations.

FIG. 10D is a block diagram of transaction information generated by thepayment module in accordance with some implementations.

FIGS. 11A-11G illustrate exemplary user interface for displayingpromotional offers in accordance with some implementations.

FIGS. 12A-12C illustrate a flowchart diagram of a method of providingand handling promotional offers for an automatic retail machine inaccordance with some implementations.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DESCRIPTION OF IMPLEMENTATIONS

Reference will now be made in detail to implementations, examples ofwhich are illustrated in the accompanying drawings. In the followingdetailed description, numerous specific details are set forth in orderto provide a thorough understanding of the subject matter presentedherein. But it will be apparent to one skilled in the art that thesubject matter may be practiced without these specific details. In otherinstances, well-known methods, procedures, components, and circuits havenot been described in detail so as not to unnecessarily obscure aspectsof the implementations.

The following clearly and completely describes the technical solutionsin the implementations of the present application with reference to theaccompanying drawings in the implementations of the present application.Apparently, the described implementations are merely a part rather thanall of the implementations of the present application. All otherimplementations obtained by persons of ordinary skill in the art basedon the implementations of the present application without creativeefforts shall fall within the protection scope of the presentapplication.

FIG. 1 illustrates a payment processing system 100. FIGS. 2-5 illustrateexample devices within the payment processing system 100. FIGS. 6A-6Cand 7 show various views of the payment module 124 and the automaticretail machine 122. FIG. 8 illustrates a schematic flow diagram of aprocess 800 for initiating a transaction within the payment processingsystem 100. FIG. 9 illustrates a schematic flow diagram of a process 900for acknowledging a transaction within the payment processing system100. FIGS. 10A-10D illustrate data structures associated with initiatingand performing transactions within the payment processing system 100.FIGS. 11A-11G illustrate example user interfaces for displayingpromotional offers. FIGS. 12A-12C illustrate a flowchart diagram of amethod 1200 of providing and handling promotional offers for anautomatic retail machine. The user interfaces in FIGS. 11A-11G are usedto illustrate the method in FIGS. 12A-12C.

Example Devices and Systems

FIG. 1 is a block diagram of a payment processing system 100 inaccordance with some implementations. In accordance with someimplementations, the payment processing system 100 includes client-sideprocessing 102-1, 102-2 (hereinafter “client-side modules 102”) executedon a mobile device 104-1, 104-2, server-side processing 106 (hereinafter“server-side module 106”) executed on a server system 108 (sometimesalso herein referred to as “the server”), and a payment module 124coupled with an automatic retail machine 122. The client-side module 102provides client-side functionalities for the payment processing system100 and communications with both the server-side module 106 and thepayment module 124. In some implementations, an application associatedwith the client-side module 102 provides a user interface to the paymentprocessing system 100 for the mobile device 104. The client-side module102 communicates with the server-side module 106 via a long-rangecommunication protocol (e.g., GSM, CDMA, Wi-Fi, or the like) through oneor more networks 110, and the client-side module 102 communicates withthe payment module 124 via a short-range communication protocol (e.g.,near-field communication (NFC), BLUETOOTH, BLUETOOTH low-energy (BLE),or the like). The server-side module 106 provides server-sidefunctionalities for the payment processing system 100 for any number ofclient modules 102 each residing on a respective mobile device 104.

The payment processing system 100 harnesses the connectivity of themobile device 104 to communicate with the payment module 124, which hasneither a dedicated communication connection nor a long-rangecommunication transceiver. As such, the mobile device 124 acts as arelay between the payment module 124 and the server system 108.Furthermore, leveraging the connectivity of the mobile device 104 helpsto keep costs down from the point of view of the operator of theautomatic retail machine 122.

In some implementations, the server-side module 106 includes one or moreprocessors 112, a user information database 114, an offers database 116,and an input and output (I/O) interface to one or more clients 118. TheI/O interface to one or more clients 118 facilitates the client-facinginput and output processing for the server-side module 106. In someimplementations, the one or more processors 112 authorize transactionrequests, determine promotional offers for a particular mobile device104, perform transaction accounting, and acknowledge completedtransactions. The user information database 114 stores information foreach user of the payment processing system 100 (e.g., user ID, accountcredentials (user name and password), transaction history, accountbalance, linked credit cards and bank accounts, and/or the like), andthe offers database 116 stores promotional offers provided bymanufacturers, distributors, retailers, and the like.

Examples of the mobile device 104 include, but are not limited to, ahandheld computer, a wearable computing device, a personal digitalassistant (PDA), a tablet computer, a laptop computer, a desktopcomputer, a cellular telephone, a smart phone, an enhanced generalpacket radio service (EGPRS) mobile phone, a media player, a navigationdevice, a game console, a television, a remote control, a point-of-sale(POS) terminal, vehicle-mounted computer, an eBook reader, or acombination of any two or more of these data processing devices or otherdata processing devices.

Examples of the one or more networks 110 include local area networks(LAN) and wide area networks (WAN) such as the Internet. One or morenetworks 110 are, optionally, implemented using any known networkprotocol, including various wired or wireless protocols, such asEthernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution(LTE), Global System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), code division multiple access (CDMA), time divisionmultiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol(VoIP), Wi-MAX, or any other suitable communication protocol.

The server system 108 is implemented on one or more standalone dataprocessing apparatuses or a distributed network of computers. In someimplementations, the server system 108 also employs various virtualdevices and/or services of third party service providers (e.g.,third-party cloud service providers) to provide the underlying computingresources and/or infrastructure resources of the server system 108. Insome implementations, the server system 108 includes, but is not limitedto, a handheld computer, a tablet computer, a laptop computer, a desktopcomputer, or a combination of any two or more of these data processingdevices or other data processing devices.

The payment processing system 100 shown in FIG. 1 includes both aclient-side portion (e.g., the client-side module 102) and a server-sideportion (e.g., the server-side module 106). In some implementations,data processing is implemented as a standalone application installed onthe mobile device 104. In addition, the division of functionalitiesbetween the client and server portions of the payment processing system100 can vary in different implementations. For example, in someimplementations, the client-side module 102 is a thin-client thatprovides only user-facing input and output processing functions, anddelegates all other data processing functionalities to a backend server(e.g., the server system 108). Although many aspects of the presenttechnology are described from the perspective of the server system 108,the corresponding actions performed by the mobile device 104 would beapparent to ones skilled in the art without any creative efforts.Furthermore, some aspects of the present technology may be performed bythe server system 108, the mobile device 104, or the server system 108and the mobile device 104 cooperatively.

FIG. 2 is a block diagram of the mobile device 104 associated with auser in accordance with some implementations. The mobile device 104,typically, includes one or more processing units (CPUs) 202, two or morecommunication devices 204, memory 206, and one or more communicationbuses 208 for interconnecting these components (sometimes called achipset). The two or more communication devices 204 include a firsttransceiver associated with a short-range communication protocol (e.g.,NFC, BLE, or the like) and a second transceiver associated with along-range communication protocol (e.g., GSM, CDMA, Wi-Fi, or the like).The mobile device 104 also includes a user interface 210. The userinterface 210 includes one or more output devices 212 that enablepresentation of media content (e.g., text, images, audio, video, etc.),including one or more speakers and/or one or more visual displays. Theuser interface 210 also includes one or more input devices 214,including user interface components that facilitate user input such as akeyboard, a mouse, a voice-command input unit or microphone, a touchscreen display, a touch-sensitive input pad, a gesture capturing camera,or other input buttons or controls. Furthermore, in someimplementations, the mobile device 104 uses a microphone and voicerecognition or a camera and gesture recognition to supplement or replacethe keyboard. In some implementations, the mobile device 104 optionallyincludes one or more sensors 215, which provide context information asto the current state of the mobile device 104 or the environmentalconditions associated with mobile device 104. The one or more sensors215 include, but are not limited, to one or more microphones, one ormore cameras, an ambient light sensor, one or more accelerometers, oneor more gyroscopes, a temperature sensor, one or more motion sensors,one or more biometric/biological sensors, and so on. In someimplementations, the mobile device 104 optionally includes a locationdetection device 217, such as a GPS (global positioning satellite) orother geo-location receiver, for determining the location of the mobiledevice 104.

The memory 206 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. The memory 206, optionally, includes one or morestorage devices remotely located from the one or more processing units202. The memory 206, or alternatively the non-volatile memory within thememory 206, includes a non-transitory computer readable storage medium.In some implementations, the memory 206, or the non-transitory computerreadable storage medium of the memory 206, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   operating system 216 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   communication module 218 for transmitting signals to and        receiving signals from other devices (e.g., the server system        108 and the payment module 124) via the two or more        communication devices 204;    -   presentation module 220 for enabling presentation of information        (e.g., a user interface for the application(s) 226 or the        application associated with client-side module 102, widgets,        websites and web pages thereof, and/or games, audio and/or video        content, text, etc.) at the mobile device 104 via one or more        output devices 212 (e.g., displays, speakers, etc.) associated        with the user interface 210;    -   input processing module 222 for detecting one or more user        inputs or interactions from the one or more input devices 214        and interpreting the detected inputs or interactions;    -   web browser module 224 for navigating, requesting (e.g., via        HTTP), and displaying websites and web pages thereof;    -   one or more applications 226 for execution by the mobile device        104 (e.g., games, application marketplaces, payment platforms,        and/or other web or non-web based applications);    -   client-side module 102, which provides client-side data        processing and functionalities for the payment processing system        100, including but not limited to:        -   broadcast obtaining module 230 for receiving, via the first            transceiver, an information packet broadcast by a respective            payment module 124, where the information packet at least            includes a unique identifier corresponding to the respective            payment module 124 (i.e., the device ID) and an            authorization code for initiating a transaction with an            automatic retail machine 122 to which the respective payment            module 124 is coupled;        -   transaction authorization module 232 for: sending, via the            second transceiver, a transaction authorization request to            the server system 108 including the authorization code;            receiving, via the second transceiver, an authorization            grant token from the server system 108, including the            authorization code, for initiating a transaction with the            automatic retail machine 122 to which the respective payment            module 124 is coupled; and storing the received            authorization grant token (e.g., in the user data 264);        -   offer(s) module 234 for: obtaining (i.e., receiving or            retrieving), via the second transceiver, promotional offers            from the server system 108 (e.g., in response to sending the            transaction authorization request, as part of an update to            the application associated with the client-side module 102,            or at another time); storing the promotional offers obtained            from the server system in the offers database 266;            optionally determining one or more promotional offers based            on one or more of a plurality of factors (e.g., the device            ID, user ID and history, current location of the mobile            device 104, current time/date, and/or the like); presenting            one or more promotional offers to the user of the mobile            device via the one or more output devices 212 (e.g., a            display); and detecting a user input selecting a respective            one of the one or more promotional offers presented to the            user of the mobile device 104;        -   trigger detecting module 236 for detecting a trigger to            initiate a transaction with the automatic retail machine 122            to which the respective payment module 124 is coupled (e.g.,            the trigger is a gesture or other user input by the user of            the mobile device 104, entrance of the mobile device 104            into a payment zone based on the RSSI observed from the            payment module 124, selection of the respective promotional            offer, or the like);        -   transaction initiating module 238 for initiating a            transaction with the automatic retail machine 122 coupled            with the respective payment module 124 by sending, via the            first transceiver, the stored authorization grant token to            the respective payment module 124;        -   transaction completion notification receiving module 240 for            receiving, via the first transceiver, a transaction            completion notification from the payment module 124, where            the transaction completion notification includes one or more            of: transaction status information (e.g., indicating whether            the transaction with the automatic retail machine 122 was            successful, aborted, or failed); transaction detail            information (e.g., the authorization code, the amount of the            transaction, the good/product associated with the            transaction, the time/date the transaction was completed,            transaction error information, and/or the like); and            optionally includes other miscellaneous information            regarding the respective payment module 124 and/or the            automatic retail machine 122 to which the respective payment            module 124 is coupled, such as interrupted transaction            information, status flags, inventory information, past hard            currency transaction information, other cashless transaction            information, and/or the like;        -   product code processing module 242 for: providing a prompt            to the user of the mobile device 104 via the one or more            output devices 212 to obtain a product code for a vended            product to validate the respective promotional offer;            obtaining the product code for the vended product (e.g., the            user of the mobile device 104 manually inputs the product            code, the user of the mobile device 104 captures an image of            the vended product from which the product code is extracted,            the user of the mobile device 104 uses a scanner plug-in of            the application associated with the client-side module 102            to obtain the product code, or the like); and either            validating the product code or sending, via the second            transceiver, the obtained product code to the server system            108 for validation;        -   information relaying module 244 for transmitting, via the            second transceiver, information from the payment module 124            to the server system 108 (e.g., the transaction status            information, the transaction detail information, the other            miscellaneous information regarding the respective payment            module 124 and/or the automatic retail machine 122 to which            the respective payment module 124 is coupled, and/or the            like);        -   offer validation module 246 for: receiving, via the second            transceiver, promotion validation information from the            server system 108; and presenting the promotion validation            information to the user of the mobile device via the one or            more output devices 212 (e.g., the display); and        -   acknowledgment module 248 for sending, via the first            transceiver, acknowledgment information to the payment            module 124, where the acknowledgment information            acknowledges that the server system 108 received and            processed the transaction status information and the            transaction detail information; and    -   client data 260 storing data associated with the payment        processing system 100, including, but is not limited to:        -   user profile 262 storing information for the user of the            mobile device 104, including but not limited to: a unique            user identifier (i.e., a user ID), login credentials (i.e.,            user name or handle and password), transaction history,            payment data (e.g., account balance, linked credit card or            bank information, app credit or gift card balance, billing            address, shipping address, etc.), contact information (e.g.,            email address, phone number, etc.), custom parameters for            the user (e.g., age, location, hobbies, etc.), identified            trends and/or likes/dislikes of the user, and/or the like;        -   user data 264 storing transaction history information,            authorization grant tokens, and/or the like; and        -   offers database 266 storing promotional offers provided by            manufacturers, distributors, retailers, and/or the like.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, modules or datastructures, and thus various subsets of these modules may be combined orotherwise re-arranged in various implementations. In someimplementations, the memory 206, optionally, stores a subset of themodules and data structures identified above. Furthermore, the memory206, optionally, stores additional modules and data structures notdescribed above.

FIG. 3 is a block diagram illustrating the server system 108 inaccordance with some implementations. The server system 108, typically,includes one or more processing units (CPUs) 112, one or morecommunication devices 304 (e.g., including the I/O interface to one ormore clients 118), memory 306, and one or more communication buses 308for interconnecting these components (sometimes called a chipset). Thememory 306 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. The memory 306, optionally, includes one or morestorage devices remotely located from the one or more processing units112. The memory 306, or alternatively the non-volatile memory within thememory 306, includes a non-transitory computer readable storage medium.In some implementations, the memory 306, or the non-transitory computerreadable storage medium of the memory 306, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   operating system 310 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   network communication module 312 for transmitting signals to and        receiving signals from mobile devices 104 via the one or more        communication devices 304;    -   server-side module 106, which provides server-side data        processing and functionalities for the payment processing system        100, including but not limited to:        -   transaction authorization module 314 for: receiving a            transaction request from a respective mobile device 104,            where the transaction request includes a device ID            associated with a respective payment module 124 and an            authorization code; and validating the transaction request;        -   encryption/decryption module 316 for: identifying an            encryption/decryption key linked to the device ID for the            respective payment module 124; decrypting the authorization            code with the identified encryption/decryption key; and            encrypting the authorization grant token with the identified            encryption/decryption key;        -   offer determining module 318 for determining one or more            promotional offers based on one or more of a plurality of            factors (e.g., the device ID included in the transaction            request, the user ID and history associated with the user of            the respective mobile device 104, current location of the            respective mobile device 104, current time/date, and/or the            like);        -   transmitting module 320 for: transmitting, in accordance            with a determination that the transaction request is            validated, an authorization grant token and the one or more            promotional offers to the respective mobile device 104; and            transmitting acknowledgment information once a transaction            is completed to the respective mobile device 104;        -   receiving module 322 for receiving information from the            respective mobile device 104, including but not limited to:            a product code and a corresponding selected promotional            offer, the transaction status information for a respective            transaction, the transaction detail information for the            respective transaction, and/or the other miscellaneous            information;        -   offer validation module 324 for: validating a promotional            offer based on a received product code, transaction status            information, and/or transaction detail information; and            sending, in accordance with a determination that the            promotional offer is validated, promotion validation            information to the respective mobile device 104;        -   accounting module 326 for debiting an account balance or            charging a linked credit card or bank account according to            the transaction detail information; and        -   acknowledgment module 328 for sending acknowledgment            information to the respective mobile device 104 for relay to            the respective payment module 124;    -   server data 340 storing data for the payment processing system        100, including but not limited to:        -   user information database 114 storing stores information for            each user of the payment processing system 100, including            but not limited to: a unique user identifier (i.e., a user            ID), login credentials (i.e., user name or handle and            password), transaction history, payment data (e.g., account            balance, linked credit card or bank information, app credit            or gift card balance, billing address, shipping address,            etc.), contact information (e.g., email address, phone            number, etc.), custom parameters for the user (e.g., age,            location, hobbies, etc.), identified trends and/or            likes/dislikes of the user, and/or the like;        -   offers database 116 storing promotional offers provided by            manufacturers, distributors, retailers, and/or the like; and        -   payment module database 342 storing information for each            payment module 124 of the payment processing system 100,            including but not limited to: a unique payment module            identifier (i.e., a device ID), an encryption/decryption            key, and/or the like.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, thememory 306, optionally, stores a subset of the modules and datastructures identified above. Furthermore, the memory 306, optionally,stores additional modules and data structures not described above.

In some implementations, at least some of the functions of the serversystem 108 are performed by the mobile device 104, and the correspondingsub-modules of these functions may be located within the mobile device104 rather than the server system 108. In some implementations, at leastsome of the functions of mobile device 104 are performed by the serversystem 108, and the corresponding sub-modules of these functions may belocated within the server system 108 rather than the mobile device 104.The mobile device 104 and the server system 108 shown in FIGS. 2-3,respectively, are merely illustrative, and different configurations ofthe modules for implementing the functions described herein are possiblein various implementations.

FIG. 4 is a schematic block diagram illustrating the automatic retailmachine 122 in accordance with some implementations. For example, theautomatic retail machine 122 is a vending machine or kiosk thatdispenses an item or product (e.g., snacks, other foodstuffs, schoolsupplies, drinks, tickets, and the like) in response to user payment forand selection of the item or product. The automatic retail machine 122includes: a controller 402; a power supply 404; memory 406; a userinterface 408; one or more optional sensors 414; a multi-drop bus (MDB)416; and a dispenser 424.

In some implementations, the controller 402 is a microcontroller,microprocessor, CPU, FPGA, ASIC, or the like that manages the functionsof the automatic retail machine 122. The power supply 404 is aconnection to an external power source (e.g., AC or DC) or a connectionto an internal power source (e.g., a battery). In some implementations,the power supply 404 further includes one or more of a power converterand/or inverter, a rectifier, a power conditioner, or the like forproviding power to the various components of the automatic retailmachine 122. The memory 406 includes high-speed random access memory,such as DRAM, SRAM, DDR RAM, or other random access solid state memorydevices; and, optionally, includes non-volatile memory, such as one ormore magnetic disk storage devices, one or more optical disk storagedevices, one or more flash memory devices, or one or more othernon-volatile solid state storage devices. In some implementations, thememory 406 stores an operating system and instructions for carrying outthe functions and processes of the automatic retail machine 122 (e.g.,dispensing items, tracking inventory, temperature control, powercontrol, and the like). In some implementations, the memory 406 alsostores configuration data and DEX (data exchange) data corresponding tothe inventory of the automatic retail machine 122 and transactionsperformed with the automatic retail machine 122.

The user interface 408 includes one or more output devices 410 thatenable presentation of information (e.g., text, images, audio, video,etc.), for example, one or more speakers and/or one or more visualdisplays. The user interface 408 also includes one or more input devices412, including user interface components that facilitate user input andselection of items such as a microphone, a keypad, a touch screendisplay, a gesture capturing camera, or other input buttons or controls.The one or more optional sensors 414 include, but are not limited, toone or more microphones, one or more cameras, an ambient light sensor,one or more accelerometers, one or more gyroscopes, a temperaturesensor, one or more motion sensors, one or more biometric/biologicalsensors, and so on.

In some implementations, a variety of payment devices are coupled withthe MDB 416 including any combination of one or more cashless paymentdevices 418 (e.g., credit card reader(s)) for accepting cashlesspayments, one or more bill validators 420 for accepting and validatingbills, and one or more coin accepters 422 for accepting coins andproviding change. In some implementations, the dispenser 424 is anelectromechanical system (e.g., motors, actuators, and the like) fordispensing or vending items or products stocked by the automatic retailmachine. 122 For example, a user inserts a bill into the billvalidator(s) 420 and is credited with an amount of money equal to thebill. Continuing with this example, the one or more output devices 410(e.g., a display) shows the credited amount, and the user selects anitem via the one or more input devices 412 (e.g., using a keypad or asequence of button presses). Subsequently, the controller 402 sendssignals to the dispenser 424 to dispense the selected product, and thedispenser dispenses or vends the selected product.

FIG. 5 is a block diagram illustrating the payment module 124 inaccordance with some implementations. In some implementations, thepayment module 124 is an in-line adapter dongle with male and femaleconnectors that couples with the multi-drop bus (MDB) of the respectiveautomatic retail machine 122 as shown in FIGS. 6B-6C and 7. For example,the payment module is connected in-line into the MDB 416 in FIG. 4. Thepayment module 124, typically, includes one or more processing units(CPUs) 512, a communication device 504 (e.g., a transceiver associatedwith a short-range communication protocol such as NFC, BLE, or thelike), memory 506, and one or more communication buses 508 forinterconnecting these components (sometimes called a chipset). Thememory 506 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. The memory 506, optionally, includes one or morestorage devices remotely located from one or more processing units 512.The memory 506, or alternatively the non-volatile memory within thememory 506, includes a non-transitory computer readable storage medium.In some implementations, the memory 506, or the non-transitory computerreadable storage medium of the memory 506, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   operating system 510 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   communication module 512 for transmitting signals to and        receiving signals from mobile devices 104 via the communication        device 504;    -   transaction-processing module 514, including but not limited to:        -   broadcasting module 516 for: broadcasting an information            packet to zero or more client devices 104 within the            communication zone of the payment module 124 (i.e., BLE            range), where the information packet at least includes a            unique identifier corresponding to the payment module 124            (e.g., the device ID) and an authorization code for            initiating a transaction with the automatic retail machine            122 to which the payment module 124 is coupled; and storing            broadcast authorization codes in authorization database 532;        -   encryption/decryption module 518 for: encrypting the            authorization code with an encryption/decryption key that            corresponds to the payment module 124; and decrypting the            authorization grant token with the encryption/decryption            key;        -   transaction sniffing module 520 for: detecting signals            associated with hard currency transactions and/or other            cashless transactions not associated with the payment            processing system 100 (e.g., credit card transactions); and            storing information associated with said hard currency            transactions and/or other cashless transactions (e.g., in            the other information database 536);        -   validating module 522 for validating a transaction by            checking the authorization code from the decrypted            authorization grant token against previously broadcast            authorization codes stored in the authorization database            532;        -   transaction processing module 524 for: causing, in            accordance with a determination that the transaction is            validated, the automatic retail machine 122 to vend a            product or perform a service; and storing transaction detail            information in the transaction database 534; and        -   acknowledgement module 526 for deleting transaction detail            information from the transaction database 534 in accordance            with a determination that the corresponding transaction is            acknowledged by the server system 108; and    -   data 530 storing data, including but not limited to:        -   authorization database 532 storing previously broadcast            authorization codes;        -   transaction database 534 storing transaction detail            information for transactions processed by the payment module            124; and        -   other information database 536 storing miscellaneous            information regarding the payment module 124 and/or the            automatic retail machine 122 coupled with the payment module            124 such as status flags, inventory information, past hard            currency transaction information, other cashless transaction            information, and/or the like.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, thememory 506, optionally, stores a subset of the modules and datastructures identified above. Furthermore, the memory 506, optionally,stores additional modules and data structures not described above.

FIGS. 6A-6C show various views of the payment module 124 of FIG. 5 inaccordance with some implementations. The payment module 124 is arelatively low cost hardware component that is pre-configured to workwith the industry standard multi-drop bus (MDB). On machines without MDBtechnology, the payment module 124 can be configured or designed to workwith other serial protocols or activate a switch (e.g., a cherry switchmechanism). For example, see U.S. patent application Ser. No.14/458,192, entitled “Method and System for Retrofitting anOffline-Payment Operated Machine to Accept Electronic Payments,” whichis incorporated by reference in its entirety. In essence, the paymentmodule 124 simulates establishing payment on the automatic retailmachine 122 in much the same manner as other alternative forms ofpayment (e.g., cash).

The payment module 124 is preferably designed to be used as an adapterdongle for in-line insertion within, for example, the MDB of theautomatic retail machine 122 (e.g., a vending machine). The wire used inMDB technology uses male and female connection ends or adapters to allowthe attachment of peripherals. In the case of a vending machine, the MDBwith connection ends or adapters would be present to allow theattachment of a payment receiving mechanism (e.g., a coin mechanism).The MDB male and female adapters 612, 614 of the MDB may be separated(as shown in FIGS. 6B-6C). The payment module 124 in FIGS. 6A-6C has amale adapter 602 and a female adapter 604. The payment module 124 may beplugged (inserted) in serial (“in-line”) with the MDB. For example, theMDB female adapter 614 may be connected to the male adapter 602 of thepayment module 124, and the MDB male adapter 612 may be connected to thefemale adapter 604 of the payment module 124. The resulting in-lineconfiguration is shown in FIG. 7. It should be noted that the paymentmodule 124 is designed to allow pass-through communications so that ifthe mobile-device-to-machine payment processing system is not enabled(e.g., for a particular purchase or simply turned off) the MDB functionsas though the payment module 124 is not there and the automatic retailmachine 122 can function normally. In FIG. 7, the automatic retailmachine 122 includes a display 722 showing user selections, currentcredit, and the like. In FIG. 7, the automatic retail machine 122 alsoincludes a touch-screen display 724 and buttons 726 for selecting aproduct.

User Interfaces and Related Processes

FIG. 8 is a schematic flow diagram of a process 800 for authenticating auser to perform a transaction in the payment processing system 100 inaccordance with some implementations. In some implementations, thepayment processing system 100 includes one or more payment modules 124(e.g., each associated with a respective automatic retail machine 122such a vending machine for dispensing goods and/or services), one ormore mobile devices 104, and the server 108. Each of the one or moremobile devices 104 executes an instance of the client-side module 102(e.g., as an application) as a foreground or background process toaccess and communicate with other devices (e.g., the server 108 and thepayment modules 124) in the payment processing system 100. The server108 manages the payment processing system 100 and, in some cases, isassociated with an entity that supplies, operates, and/or manufacturesthe one or more payment modules 124. For brevity, the process 800 willbe described with respect to a respective payment module 124 and arespective mobile device 104 within the payment processing system 100.

The payment module 124 broadcasts (802), via a short-range communicationcapability (e.g., BLE), an information packet. The information packet atleast includes an authorization code and a unique identifier associatedwith the payment module 124 (i.e., the device ID). In someimplementations, the information packet further includes a currentfirmware version of the payment module 124 and one or more status flagscorresponding to one or more states of the payment module 124 and/or theautomatic retail machine 122. The information packet is furtherdiscussed below with reference to FIG. 10A.

In some implementations, the payment module 124 sends out a uniqueauthorization code every X seconds (e.g., 100 ms, 200 ms, 500 ms, etc.).In some implementations, the unique authorization codes are randomly orpseudo-randomly generated numbers. In some implementations, the paymentmodule 124 initializes a random number and then the authorization codesare sequential counts from this random number. In such implementations,the payment module 124 stores the earliest valid (unexpired) counterwithout a need to store every valid authorization code. In someimplementations, the authentication code included in the broadcastinformation packet is a hash value of the randomly or pseudo-randomlygenerated number or the sequential number.

In some implementations, the payment module 124 stores broadcastauthorization codes (e.g., in authorization database 542, FIG. 5) untila received authorization grant token matches one of the storedauthorization codes and subsequently deletes the matching authorizationcode. In some implementations, the broadcast authorization codes areone-time use codes whereby a broadcast authorization code may only beused by one mobile device 104 before it is invalidated and/or deleted toprevent re-play attacks. In some implementations, the payment module 124stores previously broadcast authorization codes for a predeterminedamount of time (e.g., Y minutes) after which time an authorization codeexpires and is deleted. In some implementations, the authorization codeis encrypted with a shared secret key known by the server system 108 butunique to the payment module 124.

The mobile device 104 receives the broadcast information packet, and themobile device 104 sends (804), via a long-range communication capability(e.g., GSM, CDMA, Wi-Fi, or the like), an authorization request to theserver system 108. For example, an application associated with theclient-side module 102 is executed as a foreground or background processon the mobile device 104. The application is used for accessing thepayment processing system 100. In this example, the application receivesthe broadcast information packet when the mobile device 104 is withinthe communication zone of the payment module 124 (i.e., BLE range) andeither automatically sends the authorization request to the serversystem 108 or sends the authorization request to the server system 108when the mobile device 104 is within the authorization zone of thepayment module 124.

In some implementations, the broadcast information packet includes abaseline authorization zone threshold (i.e., an authorization zonecriterion) indicating a baseline received signal strength indication(RSSI) that the mobile device 104 (or the application associated withthe client-side module 102) is required to observe from the paymentmodule 124 before being within the authorization zone of the paymentmodule 124. In some implementations, the mobile device 104 (or theapplication associated with the client-side module 102) offsets thebaseline authorization zone threshold based on the reception strengthits short-range communication capability (e.g., BLE radio/transceiver)and/or other similar factors. In some implementations, the authorizationrequest at least includes the authorization code which was included inthe broadcast information packet, an identifier associated with the userof the mobile device 104 or the user account under which the user of themobile device 104 is logged into the application (i.e., user ID), andthe identifier associated with the payment module 124 (i.e., device ID).In some implementations, the authentication code included in theauthorization request is a hash value in cleartext. The authorizationrequest is further discussed below with reference to FIG. 10B.

After receiving the authorization request, the server system 108processes (806) the authorization request. In some implementations, theserver system 108 identifies a shared secret key based on the device IDand decrypts the authorization code included in the authorizationrequest with the identified shared secret key. The server system 108determines whether the user associated with the user ID in theauthorization request has sufficient funds in his/her account for thepayment processing system to perform a transaction at the automaticretail machine 122 to which the payment module 124 corresponding to thedevice ID is coupled.

The server system 108 sends (808), via a long-range communicationcapability (e.g., GSM, CDMA, Wi-Fi, or the like), an authorization granttoken to the mobile device 104. In some implementations, the serversystem 108 does not send the authorization grant token if theauthorization code in the authorization request cannot be decrypted withthe shared secret key corresponding to the payment module 124 (e.g., theauthorization code is corrupted or hacked). In some implementations, theserver system 108 does not send the authorization grant token if theuser associated with the user ID in the authorization request does nothave sufficient funds in his/her account or has exceeded a predefineddaily limit. In some implementations, in addition to the authorizationgrant token (or lack thereof if the authorization is declined), theserver system 108 sends a message directly to the mobile device 104which is not encrypted with the shared secret key corresponding to thepayment module 124. After receiving the message, the mobile device 104displays an appropriate message to the user such as sufficient funds,transaction authorized, insufficient balance, or declined authorization.In some implementations, the server system 108 sends an authorizationgrant token for an amount equal to zero; in which case, the paymentmodule 124 interprets this as a declined or failed authorization whichcan result for any number of reasons including, but not limited to,insufficient balance or credit. In some implementations, the mobiledevice 104 stores the authorization grant token (e.g., in the user data264) until a trigger condition is detected.

The mobile device 104 receives the authorization grant token, and,subsequently, the mobile device 104 detects (810) a trigger condition.In some implementations, the mobile device 104 (or the application)detects the trigger condition via the hand-free mode (e.g., uponentrance into the payment zone of the payment module 124) or manual mode(e.g., interacting with the user interface of the application toinitiate a transaction with the payment accepting unit associated withthe payment module 124).

In some implementations, the trigger condition is satisfied when themobile device 104 detects a user input on the user interface displayedby the mobile device 104. For example, with reference to FIG. 11A, atransaction is initiated between the user of the mobile device 104 andthe 8th floor snack machine when the mobile device 104 detects an upwardswipe gesture originating from region 1120 of the user interface 1108.In another example, with reference to FIG. 11D, a transaction isinitiated between the user of the mobile device 104 and the 8th floorsnack machine when the mobile device 104 detects selection of Offer A1152 with contact 1166.

In some implementations, the trigger condition is satisfied when themobile device 104 observes an RSSI from a respective automatic retailmachine that is greater than or equal to the payment zone criterion. Forexample, once the mobile device 104 is within the payment zone, atransaction between the respective automatic retail machine and the userof the mobile device 104 is automatically initiated. In someimplementations, after the RSSI observed from the respective retailmachine is greater than or equal to the payment zone criterion, themobile device 104 prompts the user to provide a transactionconfirmation, which when detected serves to satisfy the triggercondition. For example, once the mobile device 104 is within the paymentzone, the mobile device 104 provides a prompts to the user, such as anaudible prompt, displayed notification, or vibration, to confirm his/herintention to initiate a transaction with the respective retail machine.Continuing with this example, the user may confirm his/her intention toinitiate the transaction with the respective retail machine by flickingthe mobile device 104 towards the automatic retail machine, shaking themobile device, providing an audible command, or performing a touchinput/gesture on the displayed user interface.

In some implementations, unused authorization grants (e.g., if there wasno trigger condition or it expired) are canceled by the mobile device104 by sending a cancellation message to the server system 108corresponding to the unused authorization grant. In someimplementations, the server system 108 denies or limits the number ofauthorization grants sent to the mobile device 104 until it has receivedtransaction information or cancellation of authorization outstandingauthorization grants sent to the mobile device 104.

In response to detecting the trigger condition, the mobile device 104sends (812), via the short-range communication capability (e.g., BLE),the authorization grant token to the payment module 124. Subsequently,the automatic retail machine 122 displays credit to the user (e.g., viaone of the displays 722 or 724 shown in FIG. 7) and the user interactswith the input mechanisms of the automatic retail machine 122 (e.g., viathe buttons 726 or a touch screen display 724 shown in FIG. 7) topurchase products and/or services.

It should be understood that the particular order in which the processin FIG. 8 has been described is merely exemplary and is not intended toindicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods and/or processesdescribed herein (e.g., the process 900 and the method 1200) are alsoapplicable in an analogous manner to the process 800 described abovewith respect to FIG. 8.

FIG. 9 is a schematic flow diagram of a process 900 for processingacknowledgment information in the payment processing system 100 inaccordance with some implementations. In some implementations, thepayment processing system 100 includes one or more payment modules 124(e.g., each associated with a respective automatic retail machine 122such a vending machine for dispensing goods and/or services), one ormore mobile devices 104, and the server 108. Each of the one or moremobile devices 104 executes an instance of the client-side module 102(e.g., as an application) as a foreground or background process toaccess and communicate with other devices (e.g., the server 108 and thepayment modules 124) in the payment processing system 100. The server108 manages the payment processing system 100 and, in some cases, isassociated with an entity that supplies, operates, and/or manufacturesthe one or more payment modules 124. For brevity, the process 900 willbe described with respect to a respective payment module 124 coupledwith a respective automatic retail machine 122 and a respective mobiledevice 104 in the payment processing system 100. In the process 900, thepayment module 124 receives first acknowledgment information for a firsttransaction via the mobile device 104 that initiated the firsttransaction.

The payment module 124 obtains (902) a first notification indicatingcompletion of a first transaction from the automatic retail machine 122.For example, after the process 800 in FIG. 8, the user of the mobiledevice 104 selects a product to purchase from the automatic retailmachine 122 by interacting with one or more input mechanisms of theautomatic retail machine 122 (e.g., the buttons 726 or a touch screendisplay 724 shown in FIG. 7), and the automatic retail machine 122dispenses the selected product. Continuing with this example, after theproduct is dispensed, the transaction is complete and the payment module124 obtains a notification from the machine of the completedtransaction. In some implementations, the notification includes theamount of the transaction and (optionally) machine status informationassociated with the automatic retail machine 122 such as inventoryinformation as to one or more products of the automatic retail machine122 and/or the like.

After obtaining the first notification, the payment module 124 generates(904) first transaction information based on the first notification, andthe payment module 124 stores the first transaction information. In someimplementations, the transaction information includes a transaction IDfor the first transaction, a device ID corresponding to the paymentmodule 124, a user ID corresponding to the mobile device 104,transaction status information indicating that the first transaction iscomplete, and the transaction amount indicated by the firstnotification. In some implementations, the payment module 124 retainsthe authorization code included in the original broadcasted packetand/or the authorization grant token and includes the authorization codein the first transaction information. In some implementations, theauthorization code is encrypted with a secret key corresponding to thepayment module 124, which is shared with the server system 108 but notthe mobile device 104. In some implementations, the first transactioninformation further includes other information such as the machinestatus information included in the first notification or transactioninformation corresponding to previous interrupted transaction(s). SeeFIG. 10D and the accompanying text for further discussion regarding thetransaction information 1050.

The payment module 124 sends (906), via a short-range communicationcapability (e.g., BLE), the first transaction information to the mobiledevice 104.

The mobile device 104 sends (908), via a long-range communicationcapability (e.g., GSM, CDMA, Wi-Fi, or the like), the first transactioninformation to the server system 108.

The server system 108 processes (910) the first transaction information.For example, the server system 108 debits the account of the userassociated with the user ID in the first transaction information in theamount indicated by the first transaction information.

The server system 108 sends (912), via a long-range communicationcapability (e.g., GSM, CDMA, Wi-Fi, or the like), first acknowledgmentinformation to the mobile device 104. In some implementations, the firstacknowledgment information acknowledges that the server system 108received the first transaction information. In some implementations, thefirst acknowledgment information includes the user ID, the device ID,the transaction ID, and (optionally) the authorization grant included inthe transaction information (e.g., the authorization code 1058, FIG.10D).

After receiving the first acknowledgement information, the mobile device104 sends (914), via a short-range communication capability (e.g., BLE),the first acknowledgment information to the payment module 124.

After receiving the first acknowledgment information, the payment module124 deletes (916) the stored first transaction information.

It should be understood that the particular order in which the processin FIG. 9 has been described is merely exemplary and is not intended toindicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods and/or processesdescribed herein (e.g., the process 800 and the method 1200) are alsoapplicable in an analogous manner to the process 900 described abovewith respect to FIG. 9.

FIG. 10A is a block diagram of an information packet 1000 broadcast bythe payment module 124 (e.g., in step 802 of the process 800 in FIG. 8)in accordance with some implementations. In some implementations, theinformation packet 1000 at least includes: device ID 1002 andauthorization code 1004. In some implementations, the information packet1000 additionally includes: a current firmware version 1006; one or morestatus flags 1008; and zone criteria information 1010.

In some implementations, the device ID 1002 is a unique identifiercorresponding to the payment module 124 that broadcast the informationpacket 1000.

In some implementations, the authorization code 1004 is a hash value incleartext. In some implementations, the payment module 124 randomly orpseudo-randomly generates a number or determines a sequential number(See step 802 of the process 800 in FIG. 8) and performs a predeterminedhash function (e.g., SHA-256) on the number to produce the hash value asthe authorization code 1004. In some implementations, the authorizationcode 1004 is a unique code that is encrypted with a secret encryptionkey corresponding to the payment module 124. The secret encryption keyis shared with the server system 108, which enables the server system108 to decrypt the authorization code 1004 and encrypt the authorizationgrant token but not the mobile device 104. In some implementations, theencryption between server system 108 and payment module 124 isaccomplished by two pairs of public/private keys.

In some implementations, the firmware version information 1006identifies a current firmware version 1012 of the payment module 124. Insome implementations, the firmware version information 1006 alsoincludes update status information 1014 indicating one or more packetsreceived by the payment module 124 to update the firmware or one or morepackets needed by the payment module 124 to update the firmware.

In some implementations, the one or more status flags 1008 indicate astate of the payment module 124 and/or the automatic retail machine 122to which the payment module 124 is coupled. In some implementations, theone or more status flags 1008 indicate a state of the payment module 124such upload information indicator 1016 indicating that that the paymentmodule 124 has information to be uploaded to the server system 108(e.g., transaction information for one or more interruptedtransactions). In some implementations, upload information indicator1016 triggers the mobile device 104 to connect to payment module 124immediately (e.g., if it has interrupted transaction information to beuploaded to the server system 108). In some implementations, the one ormore status flags 1008 indicate a state of the automatic retail machine122 including one or more of an error indicator 1018 (e.g., indicatingthat a bill and/or coin acceptor of the automatic retail machine 122 isexperiencing a jam, error code, or malfunction), a currency levelindicator 1020 (e.g., indicating that the level of the bill and/or coinacceptor reservoir of the automatic retail machine 122 is full orempty), and/or inventory level(s) indicator 1022 (e.g., indicating thatone or more products of the automatic retail machine 122). In someimplementations, the one or more status flags 1008 are error codesissued by the automatic retail machine 122 over the MDB.

In some implementations, the zone criteria information 1010 specifies anauthorization zone criterion 1024 (e.g., a baseline authorization zonethreshold indicating a baseline RSSI that the mobile device 104 (or theapplication) is required to observe before being within theauthorization zone of the payment module 124) and/or a payment zonecriterion 1026 (e.g., a baseline payment zone threshold indicating abaseline RSSI that the mobile device 104 (or the application) isrequired to observe before being within the payment zone of the paymentmodule 124). In some implementations, the baseline authorization zonethreshold and the baseline payment zone threshold are default valuesdetermined by the server system 108 or stored as variables by theapplication, in which case the authorization zone criterion 1024 andpayment zone criterion 1026 are offsets to compensate for the strengthand/or reception of the short-range communication capability (e.g., BLEradio/transceiver) of the payment module 124. Alternatively, zonecriteria information 1010 includes a spread between the baselineauthorization zone threshold and the baseline payment zone threshold.Thus, the mobile device 104 (or the application) determines the baselineauthorization zone threshold and the baseline payment zone thresholdbased on the spread value and a default value for either the baselineauthorization zone threshold or the baseline payment zone threshold. Forexample, the spread indicates −10 db and the default baseline paymentzone threshold is −90 db; thus, the baseline authorization zonethreshold is −80 db. Continuing with this example, after determining thebaseline authorization zone threshold and the baseline payment zonethreshold, the mobile device 104 (or the application) may further adjustthe authorization zone threshold and/or the payment zone threshold basedon the strength and/or reception of its short-range communicationcapability (i.e., BLE radio/transceiver).

FIG. 10B is a block diagram of an authorization request 1030 sent by themobile device 104 to the system server 108 (e.g., in step 804 of theprocess 800 in FIG. 8) in accordance with some implementations. In someimplementations, the authorization request 1030 at least includes: adevice ID 1002; a user ID 1034; and an authorization code 1004.

In some implementations, the device ID 1002 is a unique identifiercorresponding to the payment module 124 that broadcast the informationpacket 1000 that included the authorization code 1004.

In some implementations, the user ID 1034 is a unique identifierassociated with the user of the mobile device 104 sending theauthorization request 1030 to the server system 108. In someimplementations, the user ID 1034 is associated with the user accountunder which the user of the mobile device 104 is logged into theapplication.

In some implementations, the authorization code 1030 is theauthorization code 1004 included in the information packet 1000 of thatwas broadcast by the payment module 124.

FIG. 10C is a block diagram of an authorization grant token 1040 sent bythe server system 108 to the mobile device 104 (e.g., in step 808 of theprocess 800 in FIG. 8) in accordance with some implementations. In someimplementations, in accordance with a determination that theauthorization code 1036 included in the authorization request 1030 fromthe mobile device 104 is valid and that the user associated with themobile device 104 has sufficient funds in his/her account for thepayment processing system, the server system 108 generates theauthorization grant token 1040. In some implementations, theauthorization grant token 1040 at least includes: a device ID 1002; auser ID 1034; an authorized amount 1046; (optionally) an expirationperiod 1048; and (optionally) the authorization code 1004. In someimplementations, the authorization grant token 1040 is encrypted withthe shared secret key corresponding to the payment module 124.

In some implementations, the device ID 1002 is a unique identifiercorresponding to the payment module 124 that broadcast the informationpacket 1000 that included the authorization code 1004.

In some implementations, the user ID 1034 is a unique identifierassociated with the user of the mobile device 104 that sent theauthorization request 1030 to the server system 108.

In some implementations, the authorized amount 1046 indicates a maximumamount for which the user of the mobile device 104 is authorized toperform transaction(s) using the authorization grant token 1140. Forexample, the authorized amount 1046 is predefined by the user of themobile device 104 or by the server system 108 based on a daily limit orbased on the user's total account balance or based on a risk profile ofthe user associated with the user ID 1034.

In some implementations, the expiration period 1048 indicates an offsetto the amount of time that the payment module 124 holds theauthorization grant token 1040 valid for initiation of a transactionwith the automatic retail machine 122 associated with the payment module124. For example, the expiration period 1048 depends on the history andcredit of the user of the mobile device 104 or a period predefined bythe user of the mobile device 104.

In some implementations, the authorization grant token 1040 furtherincludes the authorization code 1004 that was included in theauthorization request 1030. In some implementations, when theauthorization code 1004 is the hash value, the server system 108encrypts the authorization grant token 1040 including the hashed valuewith the shared secret encryption key associated with the payment module124. Subsequently, when the mobile device 104 sends the authorizationgrant token 1040 to the payment module 124 after detecting a triggercondition, the payment module 124 decrypts the authorization grant token1040 using the secret key known only to the server system 108 and thepayment module 124 (which authenticates the message and theauthorization grant), and then matches the hash value included in thedecrypted authorization grant token 1040 to previously broadcast valid(i.e., unexpired and un-used) hash values (e.g., stored authorizationcodes) to determine the validity of the hash value (which was known onlyby the payment module 124).

FIG. 10D is a block diagram of transaction information 1050 generated bythe payment module 124 (e.g., in step 904 of the process 900 in FIG. 9)in accordance with some implementations. In some implementations, thetransaction information 1050 includes: a transaction ID 1052 for therespective transaction; a device ID 1054; a user ID 1056; (optionally)the authorization code 1058; transaction status information 1060; thetransaction detail information 1062; and miscellaneous information 1064.In some implementations, the transaction information 1050 is encryptedwith the shared secret key corresponding to the payment module 124.

In some implementations, the transaction ID 1052 is a unique identifiercorresponding to the respective transaction. In some implementations,the transaction ID 1052 is encoded based on or associated with the timeand/or date on which and the location at which the respectivetransaction took place.

In some implementations, the device ID 1054 is a unique identifiercorresponding to the payment module 124 that performed the respectivetransaction.

In some implementations, the user ID 1056 is an identifier associatedwith the user of the mobile device 104 that initiated the respectivetransaction.

In some implementations, the authorization code 1058 corresponds to theoriginal authorization code (e.g., the auth code 1004, FIGS. 10A-10C)and/or authorization grant token (e.g., the auth grant token 1040, FIG.10C) that was used to initiate the respective transaction. In someimplementations, the authorization code 1056 is encrypted with a uniqueencryption key corresponding to the payment module 124.

In some implementations, the transaction status information 1060includes an indication whether the respective transaction was completed,not-completed, or aborted. For example, the respective transaction isincomplete if a jam occurred at the automatic retail machine 122 and theuser did not receive the product associated with the respectivetransaction. For example, if the user walks away from the automaticretail machine 122 after money was credited for the respectivetransaction, the respective transaction is aborted. In another example,if respective transaction times out after a predetermined time periodbecause the user failed to select a product at the automatic retailmachine 122, the respective transaction is aborted. In another example,if the user actuates a bill or coin return mechanism of the automaticretail machine 122, the respective transaction is aborted.

In some implementations, the transaction detail information 1062indicates the amount of the respective transaction or the amount of eachof multiple transactions (e.g., in a multi-vend scenario). In someimplementations, the transaction detail information 1062 also indicatesother information related to the respective transaction such as theitems dispensed by the automatic retail machine 122 and the type oftransaction (e.g., coins, bills, credit card, manual mode, hands-freemode, etc.).

In some implementations, the miscellaneous information 1064 includesother information related to the payment module 124 and/or the automaticretail machine 122 to which the payment module 124 is coupled. Forexample, the miscellaneous information 1064 includes a verificationrequest to the server system 108 in order to implement new firmware. Inanother example, the miscellaneous information 1064 includes transactioninformation from one or more previous interrupted transactions. Inanother example, the miscellaneous information 1064 includes transactioninformation for one or more past hard currency transactions and/or othercashless transactions (e.g., paid with a credit card or bank card at theautomatic retail machine 122). In another example, the miscellaneousinformation 1064 includes inventory information as to one or moreproducts of the automatic retail machine 122.

Attention is now directed towards implementations of user interfaces(“UIs”) and associated processes that may be implemented on a mobiledevice 104 with zero or more speakers 1102, zero or more microphones1104, and a display 1106. For example, the display 1106 is a touchscreen (sometimes also herein called a “touch screen display”) enabledto receive one or more contacts and display information (e.g., mediacontent, websites and web pages thereof, and/or user interfaces forapplication(s) 326). FIGS. 11A-11G illustrate exemplary user interfacesfor facilitating displaying promotional offers in accordance with someimplementations.

Although some of the examples that follow will be given with referenceto inputs on a touch screen (where the touch sensitive surface and thedisplay are combined), in some implementations, the device detectsinputs on a touch-sensitive surface that is separate from the display.In some implementations, the touch sensitive surface has a primary axisthat corresponds to a primary axis on the display. In accordance withthese implementations, the device detects contacts with thetouch-sensitive surface at locations that correspond to respectivelocations on the display. In this way, user inputs detected by thedevice on the touch-sensitive surface are used by the device tomanipulate the user interface on the display of the device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to contacts (e.g., finger inputs such as finger contacts,finger tap gestures, finger swipe gestures, etc.), it should beunderstood that, in some implementations, one or more of the contactsare replaced with input from another input device (e.g., a mouse-based,stylus-based, or physical button-based input). For example, a swipegesture is, optionally, replaced with a mouse click (e.g., instead of acontact) followed by movement of the cursor along the path of the swipe(e.g., instead of movement of the contact). As another example, a tapgesture is, optionally, replaced with a mouse click while the cursor islocated over the location of the tap gesture (e.g., instead of detectionof the contact followed by ceasing to detect the contact) or depressionof a physical button. Similarly, when multiple user inputs aresimultaneously detected, it should be understood that multiple computermice are, optionally, used simultaneously, or a mouse and fingercontacts are, optionally, used simultaneously.

FIGS. 11A-11G show user interface 1108 displayed on respective mobiledevice 104 (e.g., a mobile phone associated with a user) for anapplication associated with the payment processing system 100; however,one skilled in the art will appreciate that the user interfaces shown inFIGS. 11A-11G may be implemented on other similar computing devices. Theuser interfaces in FIGS. 11A-11G are used to illustrate the processesdescribed herein, including the method described with respect to FIGS.12A-12C. One of ordinary skill in the art will appreciate that thefollowing user interfaces are merely examples. Moreover, one of ordinaryskill in the art will appreciate that additional affordances and/or userinterface elements, or that fewer affordances and/or user interfaceelements may be used in practice.

FIG. 11A illustrates the mobile device 104 displaying a transactioninitiation screen 1110 for 8th floor snack machine. In FIG. 11A, thetransaction initiation screen 1110 includes a sequence of indicators1116 showing that 8th floor snack machine is one of three automaticretail machines with which the user is authorized to initiate atransaction. For example, the user of the mobile device 104 is able toaccess the second of the three automatic retail machines by performing aleft-to-right swipe gesture on the user interface 1108 (or alternativelya right-to-left swipe gesture) and the first second the three automaticretail machines by performing a right-to-left swipe gesture on the userinterface 1108 (or alternatively a left-to-right swipe gesture). Theuser of the mobile device 104 is able to access settings and/or a homescreen of the application by selecting affordance 1112 (e.g., with a tapgesture), and the user of the mobile device 104 is able to refresh thetransaction initiation screen 1110 by selecting affordance 1114 (e.g.,with a tap gesture).

FIG. 11A also shows that the user of the mobile device 104 has a prepaidbalance of $100.00. The user of the mobile device 104 is able toinitiate a transaction with the 8th floor snack machine by performing anupward swipe gesture originating from region 1120 of the transactioninitiation screen 1110. The user of the mobile device 104 is able toaccess special promotional offers by selecting “Special Offers” region1122 (e.g., with a tap gesture), and the user of the mobile device 104is able to “like” or favorite the 8th floor snack machine by selectingaffordance 1124 (e.g., with a tap gesture). FIG. 11A also illustratesthe mobile device 104 detecting contact 1140 at a location correspondingto “Special Offers” region 1122.

FIG. 11B illustrates the mobile device 104 displaying a special offersscreen 1130 for the 8th floor snack machine. In FIG. 11B, the specialoffers screen 1130 includes: a first region that corresponds to “OfferA” 1152 on product A accompanied by image A of product A; a secondregion that corresponds to “Offer B” 1154 on product A accompanied byimage A of product A; and a third region that corresponds to “Offer C”1156 on product B accompanied by image B of product B. The specialoffers screen 1130 also includes refresh affordance 1151, which, whenactivated (e.g., via a tap gesture), causes the special offers screen1130 to be refreshed. In FIG. 11B, none of Offers A, B, C are currentlyselected. The user of the mobile device 104 is able to select “Offer A”1152 by performing a gesture (e.g., a tap gesture) on selectionaffordance 1153. Similarly, the user of the mobile device 104 is able toselect “Offer B” 1154 by performing a gesture (e.g., a tap gesture) onselection affordance 1155 or “Offer C” 1156 by performing a gesture(e.g., a tap gesture) on selection affordance 1157. The user of themobile device 104 is also able to dismiss or delete any of Offers A, B,or C by performing a right-to-left swipe gesture (or a left-to rightswipe gesture in other implementations) in a corresponding region. FIG.11B also illustrates the mobile device 104 detecting a right-to-leftswipe gesture within the second region corresponding to “Offer B” 1154with contact 1160 moving from a first location 1162-a to a secondlocation 1162-b.

In some implementations, the special offers screen 1130 further includesa fourth region corresponding to “No Selected Offer.” For example, theuser of the mobile device 104 may view the promotional offers on thespecial offers screen 1130 but not wish to apply any of them to a futuretransaction with the 8th floor snack machine. As such, the user of themobile device 104 may select the “No Selected Offer” region (e.g., witha tap gesture), and, in response, the mobile device 104 re-displays thetransaction initiation screen 1110 as shown in FIG. 11A.

FIG. 11C illustrates the mobile device 104 displaying delete affordance1164 within the second region corresponding to “Offer B” 1154 inresponse to detecting the right-to-left swipe gesture in FIG. 11B. Thedelete affordance 1164, when activated, (e.g., via a tap gesture),causes “Offer B” 1154 to be deleted from the special offers screen 1130.FIG. 11C also illustrates mobile device 104 detecting contact 1166 at alocation corresponding to delete affordance 1164.

FIG. 11D illustrates the mobile device 104 ceasing to display “Offer B”1154 within the special offers screen 1130 in response to detectingselection of delete affordance 1164 in FIG. 11C. FIG. 11D alsoillustrates mobile device 104 detecting contact 1168 at a locationcorresponding to selection affordance 1153 for “Offer A” 1152.Alternatively, in some implementations, the user of the mobile devicemay not wish to apply any of the offers to a future transaction with the8th floor snack machine. As such, the user may select the affordance1112 (e.g., with a tap gesture) or perform a predefined gesture on thespecial offers screen 1130 to re-display the transaction initiationscreen 1110 as shown in FIG. 11A.

FIG. 11E shows that selection affordance 1153 is selected in response todetecting selection of selection affordance 1153 in FIG. 11D. In someimplementations, a transaction with the 8th floor snack machine isautomatically initiated in response to detecting selection of selectionaffordance 1153 in FIG. 11D. In other implementations, after detectingselection of selection affordance 1153 in FIG. 11D, the mobile device104 re-displays the transaction initiation screen 1110 (as shown in FIG.11A) and the transaction with the 8th floor snack machine is initiatedin response to detecting upward swipe gesture originating from region1120 of the transaction initiation screen 1110.

FIG. 11F illustrates the mobile device 104 displaying a product codescreen 1170, which prompts the user of the mobile device 104 to obtainthe product code (e.g., UPC code, SKU, or the like) for product A so asto validate Offer A″ 1152 selected in FIG. 11D. The product code screen1170 also includes a product code scanner window 1172 for capturing animage of product A and/or scanning the product code of product A. InFIG. 11F, UPC code 1174 (e.g., the product code) of product A (e.g., acandy bar), which is in the field of view of a camera of the mobiledevice 104, is shown within the product code scanner window 1172. Forexample, the user of the mobile device 104 is able to capture the imageof product A (including the UPC code 1174 within the current field ofview) or scan the UPC code 1174 by tapping within product code scannerwindow 1172, issuing an audible command, depressing a predeterminedphysical button of the mobile device 104, or the like. FIG. 11F alsoshows that the user of the mobile device 104 has a prepaid balance of$99.00, which is $1.00 less than the amount shown in FIGS. 11A-11E dueto purchase of product A.

FIG. 11G illustrates the mobile device 104 displaying an offervalidation screen 1180. In some implementations, the mobile device 104displays the offer validation screen 1180 after the user completes thetransaction with the 8th floor snack machine and the server validatesthe product code information (e.g., the UPC scanned in FIG. 11F). InFIG. 11G, the offer validation screen 1180 indicates that the “Offer A”1152 was validated and that the user's balance was credited $0.25. FIG.11G also shows that the user of the mobile device 104 has a prepaidbalance of $99.25, which is $0.25 more than the amount shown in FIG. 11Gdue to validation of the “Offer A” 1152 and a credit of $0.25 for the“Offer A” 1152.

FIGS. 12A-12C illustrate a flowchart diagram of a method 1200 ofproviding and handling promotional offers for an automatic retailmachine in accordance with some implementations. In someimplementations, method 1200 is performed by a mobile device with adisplay, one or more processors, and memory. For example, in someimplementations, method 1200 is performed by mobile device 104 (FIGS.1-2) or a component thereof (e.g., the client-side module 102, FIGS.1-2). In some implementations, method 1200 is governed by instructionsthat are stored in a non-transitory computer readable storage medium andthe instructions are executed by one or more processors of the mobiledevice. Some operations in the method 1200 are, optionally, combinedand/or the order of some operations is, optionally, changed.

In some implementations, the payment processing system 100 (FIG. 1)includes the mobile device 104, which performs the method 1200, a serversystem 108, and a payment module 124 coupled with an automatic retailmachine 122. An instance of the client-side module 102 (e.g., as anapplication) is executed on the mobile device 104 as a foreground orbackground process to access and communicate with other devices (e.g.,the server 108 and the payment module 124) in the payment processingsystem 100. The server 108 manages the payment processing system 100and, in some cases, is associated with an entity that supplies,operates, and/or manufactures the payment module 124.

In some implementations, prior to displaying the one or more promotionaloffers, the mobile device (1202): obtains an information packetbroadcast by a payment module coupled with a automatic retail machine,where the information packet at least includes an authorization code anda unique identifier corresponding to the payment module; send atransaction authorization request to a server, where the transactionauthorization includes the authorization code and the unique identifiercorresponding to the payment module; and, in response to the transactionauthorization request, receive authorization information from the serverthat includes an authorization grant token for initiating a transactionwith the automatic retail machine coupled with the payment module andthe one or more promotional offers from the server. As discussed in theprocess 800, the mobile device 104 or a component thereof (e.g., thebroadcast obtaining module 230, FIG. 2) receives the information packetbroadcast by the payment module 124 which at least includes anauthorization code and an identifier associated with the payment module124. Subsequently, the mobile device 104 or a component thereof (e.g.,the transaction authorization module 232, FIG. 2) sends theauthorization code to the server 108 to pre-authorize a transaction withthe automatic retail machine 122 to which the payment module 124 iscoupled. In accordance with a determination that the server 108pre-authorizes the potential transaction, the mobile device 104 or acomponent thereof (e.g., the transaction authorization module 232, FIG.2) receives an authorization grant token for performing a transactionwith the automatic retail machine 122. In some implementations, themobile device 104 stores the authorization grant token (e.g., in userdata 265, FIG. 2) until a trigger condition for initiating thetransaction with the automatic retail machine 122 is detected (e.g., bythe trigger detecting module 236, FIG. 2). In some implementations, thetrigger condition is satisfied when the mobile device 104 detects a userinput on the user interface displayed by the mobile device 104. Forexample, with reference to FIG. 11A, a transaction is initiated betweenthe user of the mobile device 104 and the 8th floor snack machine whenthe mobile device 104 detects an upward swipe gesture originating fromregion 1120 of the user interface 1108. In another example, withreference to FIG. 11D, a transaction is initiated between the user ofthe mobile device 104 and the 8th floor snack machine when the mobiledevice 104 detects selection of Offer A 1152 with contact 1166.

In some implementations, the mobile device further includes (1204) afirst transceiver associated with a short-range communication protocoland a second transceiver associated with a long-range communicationprotocol. The mobile device communicates with the payment module via thefirst transceiver, and the mobile device communicates with the servervia the second transceiver. For example, the short-range communicationprotocol is BLE, NFC, or the like, and the long-range communicationprotocol is GSM, CDMA, Wi-Fi, or the like.

The mobile device displays (1206) one or more promotional offers on thedisplay. In some implementations, the mobile device 104 only displayspromotional offers for products which the user has a sufficient balance.For example, a soda costs $2.00 and there is a promotion for $0.50 off,however, the user has a balance of only $1.00. In this example, themobile device forgoes displaying the promotion for the soda. FIG. 11B,for example, shows the mobile device 104 displaying special offersscreen 1130 for the 8th floor snack machine. In FIG. 11B, the specialoffers screen 1130 includes: a first region that corresponds to “OfferA” 1152 on product A accompanied by image A of product A; a secondregion that corresponds to “Offer B” 1154 on product A accompanied byimage A of product A; and a third region that corresponds to “Offer C”1156 on product B accompanied by image B of product B. Alternatively, insome implementations, a respective one of the one or more promotionaloffers is applied automatically after the user completes a transaction,and the mobile device prompts the user to provide the product codecorresponding to the respective promotion. In some implementations, oneor more advertisements are displayed in place of the one or moreselectable promotional offers.

In some implementations, one of the one or more promotional offers is a“reward” for a product or service that is not associated with theautomatic retail machine 122 (i.e., an out-of-band offer). For example,if the user purchases a particular product, he/she will receive a linkvia email for a free download (e.g., a song, video, etc.), in-app credit(e.g., $2.00 for purchases within a digital media marketplace or a $2.00credit for in-app purchases for a game), or the like. This may or maynot require validation of product. For example, buy any product now fromthis machine and get a link to a $1.00 off coupon via email or text fora case of soda from a retail store. In some implementations, the offermight be an “additional sale” this is an out-of-band offer. For example,purchase XYZ Cola now, and get a case of XYZ Cola from a store for only$1.50 with a coupon to be mailed to your email address. In anotherexample, purchase ABC Chips now, and get a special discount offer to buya cool T-shirt for $5.00. In this example, $5.00 is added to transactionprice and the user is sent an email regarding redemption and shipping ofthe cool the T-shirt.

In some implementations, the user is able to dismiss or delete offersand the mobile device 104 sends this information to the server 108 foranalytics purposes. In one example, FIG. 11C shows the mobile device 104displaying delete affordance 1164 within the second region correspondingto “Offer B” 1154 in response to detecting the right-to-left swipegesture in FIG. 11B. Continuing with this example, FIG. 11D shows themobile device 104 ceasing to display “Offer B” 1154 within the specialoffers screen 1130 in response to detecting selection of deleteaffordance 1164 in FIG. 11C.

In some implementations, the one or more promotional offers areidentified (1208) based on at least one of: a unique identifiercorresponding to the payment module, at least one of the current timeand date, a location of the automatic retail machine, a location of themobile device, and a unique identifier corresponding to the user of themobile device. In some implementations, the server 108 or a componentthereof (e.g., offer determining module 328, FIG. 3)determines/identifies the one or more promotional offers based on thecurrent time/date, current location, device ID associated with thepayment module, user ID associated with the user of the mobile device,and the like. In some implementations, the mobile device 104 or acomponent thereof (e.g., the offer(s) module 234, FIG. 2)determines/identifies the one or more promotional offers from apre-stored collection of offers based on the current time/date, currentlocation, device ID associated with the payment module, user IDassociated with the user of the mobile device, and the like. Forexample, the mobile device 104 identifies the one or more promotionaloffers from the offers database 266 which includes offers sent by theserver 108 at a prior time such as a part of an update to theapplication.

In some implementations, the promotional offers are identified based onthe products stocked in the automatic retail machine 122 or pastbehavior (e.g., previous offers selected by the user, previous offersdeleted by the user, previous offers not selected by the user, etc.).For example, side-by-side are separate snack and soda vending machines.The user buys a soda first. Then, when the user goes to transact withthe snack machine, the user is presented with an offer for a particularproduct (e.g., to enable cross promotions between soda and snackdistributors). Alternatively, the offers could be based on what a userdid not select from the soda machine or offers that were activelydeleted before.

In some implementations, the provider of the server 108 and paymentmodule 124 manages a promotion marketplace to facilitate placing ofpromotional offers by manufacturers and distributors of products and toalso facilitate competition between various product manufacturers anddistributors. For example, a distributor or manufacturer of a productmay place a promotional offer for $0.25 off on a particular item in allapplicable community colleges in California on Thursdays between 2:00and 4:00 PM PDT. In another example, a distributor or manufacturer of aproduct may place a promotional offer for 50% off on the product on theday the product expires (e.g., to sell perishable sandwiches or thelike) for all applicable automatic retail machines. In someimplementations, cross-promotional offers or complex promotional offersmay also be placed whereby a user gets a credit (e.g., a rebate) forpurchasing a particular drink and snack combination where each aremanufactured or distributed by different entities.

In some implementations, a promotional offer on all items in automaticretail machines on a entity's campus (essentially a subsidy) is onlyavailable to select users. For example, all attorneys and staff at a lawfirm are given a subsidized rate on snacks but cleaning persons do notbenefit from said subsidized rate. In another example, all full-timeemployees are given a subsidized rate on snacks but temporary workers donot benefit from said subsidized rate.

In some implementations, variable pricing is enacted whereby the baseprice of items changes and promotion offers may be added in addition tothe variable pricing scheme. For example, a distributer wishes todecrease the price on all items in applicable machines during theoff-peak hours (e.g., 9:00 PM-6:00 AM). Therefore, after a transactionis completed, the server 108 will only charge a user the decreasedprice, and, after the server processes and accounts for the transaction,transaction acknowledgment information displayed at the mobile device104 will indicate that the user was only charged the decreased price andnot the price shown at the automatic retail machine 122.

The mobile device detects (1210) a user input selecting a respectivepromotional offer of the one or more promotional offers. For example,the user input is a touch input, voice input, or the like. FIG. 11D, forexample, shows the mobile device 104 detecting selection of selectionaffordance 1153 for “Offer A” 1152, and FIG. 11E shows that selectionaffordance 1153 is selected in response to detecting selection ofselection affordance 1153 in FIG. 11D. In some implementations, therespective promotional offer is a negative one, such as a donation toAIDS research, that adds a selected amount to the user's nexttransaction. Alternatively, in some implementations, the respectivepromotional offer is a negative one whereby the transaction is roundedup to the nearest dollar, where additional amount is donated to a Cancerresearch foundation.

The mobile device initiates (1212) performance of a transaction with anautomatic retail machine coupled with a payment module, where thetransaction corresponds to purchase of a product stocked by theautomatic retail machine. In some implementations, the transaction isinitiated in response to selection of the respective promotional offer(i.e., one-click transaction initiation process). For example, atransaction with the 8th floor snack machine is automatically initiatedin response to detecting selection of selection affordance 1153 in FIG.11D. In other implementations, after the user selects an offer the userperforms an action to initiate a transaction with the automatic retailmachine (i.e., a two-step transaction initiation process). For example,after detecting selection of selection affordance 1153 in FIG. 11D, themobile device 104 re-displays the transaction initiation screen 1110 (asshown in FIG. 11A) and the transaction with the 8th floor snack machineis initiated in response to detecting upward swipe gesture originatingfrom region 1120 of the transaction initiation screen 1110.

In some implementations, performance of the transaction with theautomatic retail machine coupled with the payment module is initiated(1214) by sending the authorization grant token to the payment module,where the authorization grant token includes the authorization codeincluded in the broadcast information packet. In some implementations,initiating performance of the transaction includes the mobile device 104or a component thereof (e.g., the transaction initiating module 238,FIG. 2) sending the stored authorization grant token to the paymentmodule 124 for payment and the user manually selects a product using theuser interface of the automatic retail machine 122. As such, theautomatic retail machine 122 knows nothing about the selectedpromotional offer—it only knows that the user sent it a payment. Forexample, the automatic retail machine 122 returns transaction andproduct information that is passed to the mobile device 104 by thepayment module 124 but it cannot determine or state in any way if it isa product that corresponds to the offer. For example, the transactioncompletion notification indicates “I vended E3 for $1.00”.

The mobile device receives (1216) a transaction completion notificationfrom the payment module, where the transaction completion notificationindicates that the product corresponding to the selected respectivepromotional offer was vended by the automatic retail machine. In someimplementations, the mobile device 104 or a component thereof (e.g., thetransaction completion notification receiving module 240, FIG. 2)receives transaction completion notification (e.g., the transactionstatus information, the transaction detail information, the othermiscellaneous information regarding the respective payment module 124and/or the automatic retail machine 122 to which the respective paymentmodule 124 is coupled, and/or the like) from the payment module 124after the user manually selects a product using the user interface ofthe automatic retail machine 122. In some implementations, thetransaction completion notification includes the good/service associatedwith the transaction, the current inventory of the automatic retailmachine 122, information associated with one or more previous cashtransactions, information associated with one or more interruptedtransactions handled by the payment module 124, and/or other informationassociated with the automatic retail machine 122 such as error ormaintenance states. In some implementations, the payment module 124sends an error message in place of the transaction completionnotification when the transaction is aborted or an error occurs duringthe transaction such as unavailability of a requested good/service or avending jam.

In response to receiving the transaction completion notification, themobile device provides (1218) a prompt to the user of the mobile deviceto obtain a product code for the vended product to validate therespective promotional offer. In some implementations, the mobile device104 or a component thereof (e.g., the product code processing module242, FIG. 2) displays a scanning interface for capturing the productcode of the vended item after receiving the transaction completionnotification. FIG. 11F, for example, shows the mobile device 104displaying a product code screen 1170, which prompts the user of themobile device 104 to obtain the product code (e.g., UPC code, SKU, orthe like) for product A so as to validate Offer A″ 1152 selected in FIG.11D. The product code screen 1170 also includes a product code scannerwindow 1172 for capturing an image of product A and/or scanning theproduct code of product A. In FIG. 11F, the UPC code 1174 of product A(e.g., a candy bar), which is in the field of view of a camera of themobile device 104, is shown within the product code scanner window 1172.For example, the user of the mobile device 104 is able to capture theimage of product A (including the UPC code 1174 within the current fieldof view) or scan the UPC code 1174 by tapping within product codescanner window 1172, issuing an audible command, depressing apredetermined physical button of the mobile device 104, or the like.

In other implementations, the mobile device 104 or a component thereof(e.g., the product code processing module 242, FIG. 2) displays a pop-upmessage or banner notification on the display prompting the user of themobile device 104 to manually enter or otherwise obtain the product codeof the vended item. In other implementations, the mobile device 104 or acomponent thereof (e.g., the product code processing module 242, FIG. 2)provides an audible tone, a vocal prompt, or a sequence oftactile/haptic vibrations prompting the user of the mobile device 104 toenter or otherwise obtain the product code of the vended item.

The mobile device obtains (1220) the product code for the vendedproduct. For example, the user enters the barcodecharacter-by-character, scans the barcode, or simply captures an imageof the barcode. In some implementations, the mobile device 104 or acomponent thereof (e.g., the product code processing module 242, FIG. 2)receives the product code.

In some implementations, obtaining the product code further comprises(1222): capturing an image of the product that includes the productcode; and extracting the product code from the captured image. In someimplementations, obtaining the product code further comprises (1224):scanning the product code of the product with a scanner unit of themobile device. For example, the user of the mobile device 104 is able toaccess a product code capture plug-in from within the applicationassociated with the payment processing system 100 (e.g., the productcode processing module 242, FIG. 2) which enables the user to capture animage of the product with the product code in the field of view or scanthe product code of the product. In this example, the mobile device 104extracts the product code from the captured image and sends theextracted product code to the server 108 or, alternatively, the mobiledevice 104 sends the captured image to the server 108 where the productcode is extracted. In another example, the user of the mobile device 104is able to manually enter the product code from within the application(e.g., via a virtual keypad) or via a website associated with thepayment processing system 100.

After obtaining the product code, the mobile device transmits (1226) theproduct code to the server. In response to transmitting the productcode, the mobile device: receives promotion validation information fromthe server; and displays the promotion validation information on thedisplay, where the promotion validation information indicates whetherthe respective promotion offer was validated. In some implementations,the mobile device 104 or a component thereof (e.g., the product codeprocessing module 242, FIG. 2) either validates the obtained productcode or sends the obtained product code to the server 108 forvalidation. In some implementations, the mobile device 104 or acomponent thereof (e.g., the information relaying module 244, FIG. 2)sends the transaction completion notification or a portion thereof tothe server 108 regardless of whether the user follows the prompt and themobile device 104 ultimately obtains the product code. In someimplementations, the server 108 determines whether conditions for therespective promotional offer have been based on the transaction and theproduct code. For example, the server 108 determines whether the properproduct code was obtained for the respective promotional offer, whetherthe respective promotional offer has expired, whether the user hasfulfilled a buy N items get one free condition, whether the user hasfulfilled cross-promotion condition, and/or the like. In someimplementations, the offer is validated and applied by the server 108 tothe user's account.

In some implementations, the mobile device 104 of a component thereof(e.g., the offer validation module 246, FIG. 2) receives and displaysthe promotion validation information. For example, the promotionvalidation information indicates whether the offer was validated and anupdated user balance/transaction listing. FIG. 11G, for example, showsthe mobile device 104 displaying an offer validation screen 1180, whichindicates that the “Offer A” 1152 was validated and that the user'sbalance was credited $0.25. FIG. 11G also shows that the user of themobile device 104 has a prepaid balance of $99.25, which is $0.25 morethan the amount shown in FIG. 11G due to validation of the “Offer A”1152 and a credit of $0.25 for the “Offer A” 1152. For example, when theuser gets a fifth purchased product free and the product that was thesubject of the instant transaction was only the first item purchased,the promotion validation information indicates that the user must buy 3more of the product before he/she gets a free product. In someimplementations, the promotion validation information includes a couponfor a product or service that is not associated with the automaticretail machine 122 For example, the user is emailed a coupon for $5 offan amusement park for purchasing a soda.

In some implementations, after obtaining the product code, the mobiledevice determines (1228) whether a predetermined time period hasexpired. In accordance with a determination that the time period hasexpired, the mobile device provides a notification to the user of mobiledevice indicating that the respective promotional offer has expired. Inaccordance with a determination that the time period has not expired,the mobile device transmits the product code to the server. In someimplementations, the predetermined time period corresponds to the timebetween (A) initiating performance of the transaction or prompting forthe product code, (B) obtaining the product code or some other timeperiod. For example, the mobile device 104 must receive the product codewithin 5 minutes of the prompt or within 5 minutes of initiation of thetransaction. In some implementations, this may occur hours or even dayslater. In some implementations, a predetermined proximity between afirst location where the transaction was initiated and a second locationwhere the product code was obtained is used in addition to or in placeof the predetermined time period.

In some implementations, the application associated with the paymentprocessing system 100 has a coupon plug-in whereby the user of themobile device 104 is able to scan a coupon after completing atransaction for a product and also scan the product code of the productto get a post hoc rebate for the transaction.

In some implementations, the promotion validation information indicates(1230) the price of the product after the application of the respectivepromotional offer. For example, the mobile device 104 displays the totaldeducted from the user's account or charged to the user's linked bankcard after application of the promotional offer to the base purchaseprice included in the notification completion information. FIG. 11G, forexample, shows that the user of the mobile device 104 has a prepaidbalance of $99.25, which is $0.25 more than the amount shown in FIG. 11Gdue to validation of the “Offer A” 1152 and a credit of $0.25 for the“Offer A” 1152.

In some implementations, the mobile device transmits (1232) thetransaction completion notification to the server. In someimplementations, the mobile device 104 or a component thereof (e.g., theinformation relaying module 244, FIG. 2) sends the transactioncompletion notification (e.g., the transaction status information, thetransaction detail information, the other miscellaneous informationregarding the respective payment module 124 and/or the automatic retailmachine 122 to which the respective payment module 124 is coupled,and/or the like) or a portion thereof to the server 108 prior to sendingthe product code or along with the product code. In someimplementations, the transaction completion notification or a portionthereof is sent to the server 108 regardless of whether the user followsthe prompt and the mobile device ultimately obtains the product code.

It should be understood that the particular order in which theoperations in FIGS. 12A-12C have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods and/or processesdescribed herein (e.g., the processes 800 and 900) are also applicablein an analogous manner to method 1200 described above with respect toFIGS. 12A-12C.

While particular implementations are described above, it will beunderstood it is not intended to limit the application to theseparticular implementations. On the contrary, the application includesalternatives, modifications and equivalents that are within the spiritand scope of the appended claims. Numerous specific details are setforth in order to provide a thorough understanding of the subject matterpresented herein. But it will be apparent to one of ordinary skill inthe art that the subject matter may be practiced without these specificdetails. In other instances, well-known methods, procedures, components,and circuits have not been described in detail so as not tounnecessarily obscure aspects of the implementations.

What is claimed is:
 1. A method, comprising: at a mobile deviceincluding a display, one or more processors, a communications unit, andmemory: identifying a retail machine configured for wirelesscommunications; transmitting via the communications unit of the mobiledevice an identifier corresponding to the retail machine to a server andreceiving from the server an electronic communication including one ormore promotional offers for products offered by the retail machine;displaying on the display of the mobile device the one or morepromotional offers; detecting selection of a respective promotionaloffer of the one or more promotional offers; receiving, via thecommunications unit, notification information from the retail machineassociated with provision of a product by the retail machine for a userof the mobile device; in response to receiving the notificationinformation associated with the provision of the product by the retailmachine: capturing, with a camera or scanner of the mobile device, animage or scan of the product provided by the retail machine, the imageor scan including a product code of the product provided by the retailmachine; and transmitting to the server via the communications unit ofthe mobile device the product code of the product provided by the retailmachine and the notification information associated with the provisionof the product; and in response to transmitting the product code and thenotification information to the server: receiving, via thecommunications unit, promotion validation information from the serverindicating validation of the respective promotional offer of the one ormore promotional offers; and based on the promotion validationinformation, displaying on the display information confirmingapplication of the respective promotional offer.
 2. The method of claim1, wherein the product that was provided is part of a transactionassociated with the user of the mobile device, and further wherein thepromotion validation information includes promotion validationinformation with respect to the transaction.
 3. The method of claim 2,wherein the one or more promotional offers are displayed within a firstuser interface for an application executing on the mobile device.
 4. Themethod of claim 3, wherein the promotion validation information isdisplayed within a second user interface for the application executingon the mobile device.
 5. The method of claim 4, wherein displaying thepromotion validation information includes displaying an indication as towhether the respective promotional offer was validated and displayinginformation identifying a credit to the user associated with therespective promotional offer.
 6. The method of claim 1, furthercomprising, before detecting selection of a respective promotionaloffer, receiving the one or more promotional offers based at least inpart on particular products offered by the retail machine.
 7. The methodof claim 6, wherein selecting the one or more promotional offers isfurther based at least in part on at least one previous transactioncompleted by the user at a different retail machine that is distinctfrom the retail machine.
 8. The method of claim 1, wherein the selectedrespective promotional offer is associated with both a time-basedcondition that is satisfied by using the selected respective promotionaloffer within a predetermined time period and a product-based conditionthat is satisfied by determining that the product provided by the retailmachine qualifies for the selected respective promotional offer.
 9. Themethod of claim 8, wherein the promotion validation information includesan indication as to whether (i) the time-based condition and (ii) theproduct-based condition were satisfied.
 10. The method of claim 1,further comprising: while displaying on the display of the mobile devicethe one or more promotional offers, detecting a request from the user todismiss a particular promotional offer of the one or more promotionaloffers; and in response to detecting the request: (i) ceasing to displaythe particular promotional offer on the display and (ii) sending, viathe communications unit, information indicating that the user dismissedthe particular promotional offer.
 11. The method of claim 1, furthercomprising: after receiving the notification information, determiningwhether a predetermined time period has expired; in accordance with adetermination that the predetermined time period has expired, providinga communication to the user of the mobile device indicating that therespective promotional offer has expired; and in accordance with adetermination that the predetermined time period has not expired,transmitting the product code and the notification information to theserver.
 12. The method of claim 1, further comprising: prior todisplaying on the display of the mobile device the one or morepromotional offers: obtaining an information packet broadcast by theretail machine, wherein the information packet at least includes anauthorization code and a unique identifier corresponding to the retailmachine; sending a transaction authorization request to the server,wherein the transaction authorization includes the authorization codeand the unique identifier corresponding to the retail machine; and inresponse to the transaction authorization request, receiving from theserver: (i) authorization information that includes an authorizationgrant token for initiating a transaction with the retail machine, and(ii) the one or more promotional offers.
 13. The method of claim 12,further comprising, before receiving the notification information,initiating performance of a transaction with the retail machine bysending the authorization grant token to the retail machine, wherein theauthorization grant token includes the authorization code included inthe information packet.
 14. The method of claim 13, wherein thetransaction is initiated in response to detecting the selection of therespective promotional offer.
 15. The method of claim 1, furthercomprising, in response to receiving the notification information:providing a prompt instructing the user of the mobile device to confirmthat the product was provided; and capturing the image or scan inresponse to the prompt.
 16. The method of claim 15, wherein the productcode is a universal product code (UPC) corresponding to the product, andobtaining the product code comprises capturing, with a camera of themobile device, an image of the product that includes the UPC.
 17. Themethod of claim 15, wherein the product code is a universal product code(UPC) corresponding to the product, and obtaining the product codecomprises scanning, with a scanner of the mobile device, an area of theproduct that includes the UPC.
 18. The method of claim 1, wherein theone or more promotional offers are based at least in part on theidentifier corresponding to the retail machine.
 19. A mobile device,comprising: a display; a communications unit; one or more processors;and memory storing one or more programs to be executed by the one ormore processors, the one or more programs comprising instructions for:identifying a retail machine configured for wireless communications;transmitting via the communications unit of the mobile device anidentifier corresponding to the retail machine to a server and receivingfrom the server an electronic communication including one or morepromotional offers for products offered by the retail machine;displaying on the display of the mobile device the one or morepromotional offers; detecting selection of a respective promotionaloffer of the one or more promotional offers; receiving, via thecommunications unit, notification information from the retail machineassociated with provision of a product by the retail machine for a userof the mobile device; in response to receiving the notificationinformation associated with the provision of the product by the retailmachine: capturing, with a camera or scanner of the mobile device, animage or scan of the product provided by the retail machine, the imageor scan including a product code of the product provided by the retailmachine; and transmitting to the server via the communications unit ofthe mobile device the product code of the product provided by the retailmachine and the notification information associated with the provisionof the product; and in response to transmitting the product code and thenotification information to the server: receiving, via thecommunications unit, promotion validation information from the serverindicating validation of the respective promotional offer of the one ormore promotional offers; and based on the promotion validationinformation, displaying on the display information confirmingapplication of the respective promotional offer.
 20. A non-transitorycomputer readable storage medium storing one or more programs, the oneor more programs comprising instructions, which, when executed by amobile device with a display, a communications unit, and one or moreprocessors, cause the mobile device to perform the functions of:identifying a retail machine configured for wireless communications;transmitting via the communications unit of the mobile device anidentifier corresponding to the retail machine to a server and receivingfrom the server an electronic communication including one or morepromotional offers for products offered by the retail machine;displaying on the display of the mobile device the one or morepromotional offers; detecting selection of a respective promotionaloffer of the one or more promotional offers; receiving, via thecommunications unit, notification information from the retail machineassociated with provision of a product by the retail machine for a userof the mobile device; in response to receiving the notificationinformation associated with the provision of the product by the retailmachine: capturing, with a camera or scanner of the mobile device, animage or scan of the product provided by the retail machine, the imageor scan including a product code of the product provided by the retailmachine; and transmitting to the server via the communications unit ofthe mobile device the product code of the product provided by the retailmachine and the notification information associated with the provisionof the product; and in response to transmitting the product code and thenotification information to the server: receiving, via thecommunications unit, promotion validation information from the serverindicating validation of the respective promotional offer of the one ormore promotional offers; and based on the promotion validationinformation, displaying on the display information confirmingapplication of the respective promotional offer.